Contact Data Object

Contents of the Data Object

The contact data object contains all the relevant data about the

 

PERSON and ORG

with the contact data:

  • unique handle,

  • domain owners,

  • address,

  • email,

  • telephone number,

  • verification information,

 

REQUEST

with the contact details (for General Request or Abuse Contact):

  • unique handle,

  • URI template.

 

Processing Options

You can use the request forms Contact CREATE and Contact UPDATE to establish a new Contact or to change an existing one.

 

Structure and rules for contacts of the types PERSON and ORG

K/V Keyword XML Namespace and Element Occurrence
min - max		 Type / Length Value Range Description Policy
Handle contact:handle 1 token
9 - 32 		contact-rule This is the unique ID of the Contact.Syntax: <RegAccId>-<MemberID >
  • A Contact handle must always start with the RegAccId of the administering RegAcc.
Type contact:type 1 enumeration role-erule These Contact types are available:
  • PERSON = natural person,
  • ORG = a legal person (company, association, grouping of holders, organization etc., such as "DENIC eG")
  • The type of contact can be changed later.
  • For Holder you may only use the types PERSON or ORG.
Name contact:name 1 normalizedString
1 - 255 		name-rule This is the Contact's name.
  • Once set, you cannot change the keyword "name" any more.
Organisation contact:organisation 0 - * normalizedString
1 - 255 		organisation-rule This is the organisation which is represented by the Contact.
  • You may only use the types PERSON.
  • Cannot be changed, if the domain bears a DISPUTE entry.
  • You must always state the domain holder in the "Name:" field. The "Organization" value has no right to the domain and is not entitled to apply for an AuthInfo or a provider change or similar.
Address contact:address 1 - * normalizedString
1 - 255 		address-rule Street and house number of Contact The keyword cannot be changed if the Contact is referenced as the holder of a domain which bears a DISPUTE entry.
PostalCode contact:postalCode 1 token
1 - 20 		postalcode-rule Postal code and address of Contact The keyword cannot be changed if the Contact is referenced as the holder of a domain which bears a DISPUTE entry.
City contact:city 1 normalizedString
1 - 80 		city-rule Place of residence of Contact The keyword cannot be changed if the Contact is referenced as the holder of a domain which bears a DISPUTE entry.
CountryCode contact:countryCode 1 Enumeration
2 		country-erule Country code of the country in which the Contact's place of residence is located
  • You must use the country code of the ISO-3166-1 alpha-2 list ISO-3166-1 alpha-2 Liste.
  • The keyword cannot be changed if the Contact is referenced as the holder of a domain which bears a DISPUTE entry.
Email contact:email 1 - * normalizedString
3 - 255 		email-rule

(see RFC5322 - Internet Message Format)		 E-mail address of Contact „email” always is a mandatory field and must be specified at least once for the types PERSON and ORG in Contact CREATE and Contact UPDATE requests

Contact Data Object: Syntax and Processing Rules for Contacts of the REQUEST Type

The table below informs about the contacts of the REQUEST type.

K/V Keyword XML Namespace and Element Occurrence
min - max		 Type / Length Value Range Description Policy
Handle contact:handle 1 token
9 - 32 		contact-rule This is the unique ID of the Contact.Syntax: <RegAccId>-<MemberID > A Contact handle must always start with the RegAccId of the administering RegAcc.
Type contact:type 1 enumeration role-erule REQUEST = an e-mail address or a URL in the URI-Template format. For General Request and Abuse Contact you may only use the type REQUEST.
URI-Template contact:uri-template 1 normalizedString
8 - 1024 		Syntax as defined in RFC 6570 - URI Template The variables Ulabel and Alabel in the URI-Template are replaced with the domain at a domain query (web-whois). In case of a CREATE request, the content of the URI-Template is converted into a URL or e-mail as a test (For Alabel and Ulabel, a sample domain is used.) to check the syntax on correctness.